IBM 8270, 8271 AND 8272 LAN SWITCH ATM UFC RELEASE NOTES - VERSION 1.15.5 Edited October 26, 1999 This set of release notes provides specific information for software release 1.15.5 for the ATM UFCs for IBM 8270, 8271 and 8272 LAN Switch, and for the 8271 and 8272 LAN Switch Modules with an integrated ATM port. It documents important operating environment considerations. The term ATM UFC refers to both the ATM Universal Feature Card and the integrated ATM port, unless otherwise noted. Detailed instructions are contained in the Planning and Installation Guide titled: * ATM 155-Mbps Multimode Fiber Universal Feature Card - Planning and Installation Guide (GA27-4156) Updates to the release notes and switch software will be posted on the Internet and can be obtained using the World Wide Web URL: http://www.networking.ibm.com/support ------------------------------------------------------------------------ * Table of Contents Latest Release Level of Software ATM UFC Software Corequisites Problems Fixed in the ATM UFC Software o Release 1.15.5 o Release 1.15.4 Release 1.15.3 Release 1.15.1 Release 1.15.0 Release 1.14.2 Release 1.14.0 Release 1.12.3 Release 1.11.0 Release 1.10.0 Known Problems / Anomalies / Design Points 8260/8265 Specific Information Files on the Diskettes and Software Download Procedures o IBM 827X ATM UFC Microcode and SNMP MIB Diskette - Release 1.15.5 Loading the Latest ATM UFC Main Image Loading the ATM UFC boot(strap) Image ------------------------------------------------------------------------ Latest Release Level of Software If the publications package that came with the product contains a set of release notes and diskette inside the shrink-wrapped package, they may be down-level and should be discarded. This set of release notes and diskette are the latest level as of the manufacturing date of your switch. Any updates to the release notes and switch software will be posted on the Internet and can be obtained using the World Wide Web URL: http://www.networking.ibm.com/support It is important to check the Web site to ensure that you are using the latest level of software. This release of the ATM UFC software is a maintenance release which provides support for Emulated LANs (ELANs) on the 155 Mb/s ATM Universal Feature Card (UFC). The ATM UFC provides a LAN Emulation Proxy Client service, which in conjunction with the LAN Emulator Server functions within the ATM network, allows Token-Ring or Ethernet-attached stations to communicate with servers attached directly to ATM switches (e.g. 8265 ATM Campus Switch) or with stations or servers located on other 8270, 8271, or 8272 switches across the ATM Backbone. ATM UFC Software Corequisites * The ATM UFC Code Release listed is compatible with the Switch Code Release(s) listed below: ATM UFC Release 8270/8272 Release 8271 Release 1.15.5 5.2, 5.2.1 5.1 (no change) 1.15.4 5.2, 5.2.1 5.1 (no change) 1.15.3 5.1.1, 5.2 5.1 (no change) 1.15.1 5.1.1 5.1 (no change) 1.15.0 5.1 5.1 1.14.2 4.03, 5.01 4.0 1.12.3 3.6.1 3.5.5 1.11.0 3.2.3 3.5.3 1.10.0 3.2.2 3.5.2 IMPORTANT Software for the base LAN Switch and ATM UFC must always be upgraded simultaneously. For example, a user currently running code versions 4.0.3 for the base switch and 1.14.2 for the ATM UFC should upgrade to 5.2.1 and 1.15.5. A mixture of code levels (e.g. 3.2.3 and 1.14.2 for instance) is not supported. Problems Fixed in the ATM UFC Software * Release 1.15.5 Connectivity 1. If a route descriptor source moved from one token-ring port to another on the same switch, the route descriptor could become unregistered in the legacy table. This could also happen in instances where the source entry was aged out and re-learned immediately, even if the source had not moved. * Release 1.15.4 Connectivity 1. When the ATM UFC was connected to a Fore ATM switch, and both ends of the link were set to autodetect the UNI version, signalling would not work after the link was broken, even after the link was re-established. 2. The ATM UFC would respond to an ILMI get for atmfAtmLayerUniType with noSuchName, instead of 2 for Private UNI. This caused a warning message in Fore ATM switches. * Release 1.15.3 Reliability 1. An invalid frame may be propagated over the network by the LAN switch ports when large amounts of small frames are received by the ATM UFC. The invalid frame will contain 20 bytes of random data, not including the CRC. This problem has been fixed. Connectivity 1. In heavy traffic conditions the ATM port could momentarily be declared "DOWN". The ATM UFC would send an "ILMI cold start" trap and re-initialize the link immediately. This caused a traffic outage of a few seconds depending on the setting of the 802.1d spanning tree "forward delay" parameter. This problem has been fixed. Release 1.15.1 Connectivity 1. Under certain conditions, the first IP datagram or IPX frame for a MAC address was lost. This could cause session establishment to fail or be delayed. The problem has been fixed. 2. With version 1.15.0, many "link down" traps were generated by an integrated ATM port when the port was disabled at the 826x. The same problem also occurred with an ATM UFC port when its 826x port was isolated. This problem has been fixed. Release 1.15.0 Reliability 1. A problem with SAAL handling link errors requiring the retransmission of multiple packets has been fixed. 2. The ATM UFC may be reset as a result of an "Echo time-out" due to an ATM UFC specific internal error (FAULT PC=600, FAULT PC=200, or other reasons). This problem was observed only in a lab stress environment. 3. Additional internal diagnostic capabilities have been added to enable quicker data collection in the case of a problem. Connectivity 1. UNI Version autodetect did not work if the attached ATM switch reported UNI 4.0 as the highest version supported. In release 1.15.0, the ATM UFC and the attached ATM switch correctly negotiate to UNI 3.1 which is the highest version that BOTH devices support. This problem was observed when using FORE ATM switches. Performance 1. Release 1.15.0 adds support for receiving targetless LE_ARP REQUESTS. Targetless LE_ARP REQUESTS are issued by the MSS Redundant Default Gateway (and by the MSS Distributed Gateway Function) when the active gateway changes. This alerts all the members of the ELAN that the ATM address of the active gateway has changed and packets for the gateway should be sent to the new address. This support, first available with MSS Release 2.1 improves the discovery time of a newly active gateway. Release 1.14.2 Reliability 1. ATM UFC release 1.14.0 is not compatible with 8265 CPSW version F3.3.4 and prior 8265 CPSW versions. (8260 users are not affected by this problem.) A problem with the encoding of the system up-time by the ILMI code on the ATM UFC caused the 8265 to reset the ILMI layer at certain times after the 827x was powered on. The ILMI layer resets 10 minutes after the 827x completes diagnostics and again 46 hours later with CPSW version F3.3.4. With earlier CPSW versions the resets occur at the 5 minute mark and at the 23 hour mark. The resets do not occur if ATM UFC Release 1.14.2 is used. 2. The serial download function in ATM UFC Release 1.13.0 through 1.14.1 does not work. If serial download of ATM UFC code is attempted, the operation will hang and a complete 827x switch reset is required to clear the condition. Also, if the ATM UFC main image becomes corrupted (e.g. if the 827x or the ATM UFC is reset during ATM UFC code download) an ATM UFC with these releases of boot(strap) code can not be restored and the UFC is rendered permanently inoperable. It is NOT recommended to install any of the defective releases of boot(strap) code. ATM UFC Release 1.14.2 contains a fixed version of the boot(strap) code. If you need to install this level then see the section titled Loading the ATM UFC boot(strap) Image for boot code upgrade instructions. Release 1.14.0 Reliability 1. The ATM UFC may be reset as a result of an "Echo time-out" due to an ATM UFC specific internal error (FAULT PC=600, FAULT PC=200, or other reasons). These problems have been fixed. Connectivity 1. The ATM UFC LEC(s) failed to rejoin the ELAN under certain recovery scenarios. These problems have been fixed. 2. The ATM Campus Manager could not discover and manage an 827x attached to an 8260/8265 using ATM. This problem has been fixed. 3. Heavy LAN port traffic coinciding with overflowing LAN port address tables could cause data, control or multicast VCCs to drop. This has been fixed. 4. Under rare circumstances, an ATM address may never be resolved for a destination MAC address. This problem has been fixed. 5. Particularly in networks with many ATM devices which periodically (but routinely) disconnect from the ATM network, the ATM UFC would occasionally lose information about certain VCCs (data, control, or multicast) causing the VCC to appear "UP" when in fact frames on that VCC were being discarded. This problem has been fixed. 6. Under certain conditions, a discrepancy existed between the ATM UFC and the 826x on what UNI version should be used. This problem has been fixed. 7. When an integrated ATM port was "isolated" from the 826x console, the port would fail to show "DOWN" on the 827x console. This problem has been fixed. Performance 1. The time required to detect a LES/BUS outage has been shortened to 4 seconds. Previously it could take up to 32 seconds using UNI 3.1 or 90 seconds using UNI 3.0 to detect certain LES/BUS outages. This new LES/BUS failure detection mechanism monitors traffic from the LES/BUS. When used in a network that includes a redundant LES/BUS this new mechanism will provide quicker switchover times from a primary LES/BUS to an alternate LES/BUS if the primary LES/BUS fails. See item 10, Data Direct Keep Alive Timeout in the section titled Known Problems / Anomalies / Design Points later in this document. 2. The domain mac address previously was registered as a LOCAL address. When a topology change occurred in the network, other LECs could take up to their configured C17 time (default is 5 minutes) to re-discover LOCALLY registered macs. The domain mac address is now registered as a REMOTE address to improve the rediscovery of the ATM UFC LEC by other LECs following a topology change. 3. Particularly in networks with many ATM devices which periodically (but routinely) disconnect from the ATM network, timers associated with the le-arp table in the ATM UFC would become stuck, preventing proper table maintenance. This problem has been fixed. Release 1.12.3 Connectivity 1. The LE ARP cache size has been increased to 3400 entries. In the case of LE ARP cache overflow, the ATM UFC will now reuse entries in the LE ARP cache. 2. LE ARP cache entries management has been improved, preventing connection or session loss. 3. A problem with the first frame getting lost has been corrected. This problem prevented connection from being established or caused session loss. 4. An ATM port reset or a LEC reset was sometimes required to get the LEC to rejoin the ELAN after a failure. The LEC now rejoins automatically. 5. When a LEC ID changed, the old LEC ID was still used by the data direct VCC. This restricted communication with a device that has the old LEC ID. The ATM UFC code is now aware of the LEC ID changes. The user no longer has to set the Data Direct VCC Keep Alive Timeout to zero to bypass this problem. Performance 1. ATM UFC load (Boot) time is four times faster than previous releases. In order to make this active, the user must load this release of ATM UFC boot code. See the section titled Loading the ATM UFC boot(strap) Image for boot code upgrade instructions. 2. ATM UFC's re-assembly buffers recovery has been improved, preventing network "slowdowns" and ATM UFC hangs. 3. The frame processing power of the ATM UFC has been improved, providing faster registration, address learning, and cell reception and transmission. Release 1.11.0 1. A data corruption problem has been fixed in this release. Users connected through IBM 8270/8272 LAN Switch ATM UFC experienced SNA session loss. A frame received from the ATM network was duplicated as it was passed to a Token-Ring port. This problem has been corrected. All users (8271/8270/8272) should upgrade the ATM UFC code to Release 1.11.0 2. The IBM 827x LAN Switch cold boot diagnostic could incorrectly detect a loopback test failure and disable the ATM UFC. This problem has been corrected. 3. An ATM UFC port reset was sometimes required if a LAN Emulation Client failed to rejoin the Emulated LAN after a heavy traffic condition with many learned addresses. This problem has been corrected. 4. The AFC console has been enhanced in this release. 5. A problem where end-station to end-station connectivity across the ATM network was lost has been corrected. Heavy traffic with many learned addresses could cause an out of buffer condition on the ATM UFC. Under this condition, the ATM UFC did not update the hardware filter tables that map MAC addresses to Virtual Circuit Identifiers to maintain end-station to end-station connectivity. 6. An ATM UFC port reset was sometimes required when the ATM UFC reported "port is DOWN". The ATM UFC failed to restart the ILMI communication when the IBM 8260 155 blade was initially in ISOLATED mode, and then moved to CONNECTED/ENABLED or the IBM 8260 was reset. This problem has been corrected. 7. A problem handling multiple incoming calls from the same LAN Emulation Client is fixed in this release. Normally, an ATM LAN emulation Client will make only one call at a time to the same destination and this code problem will not be apparent. However, certain misbehaving ATM LAN Emulation Client device drivers can issue many such calls and fill up the ATM UFC's data direct VCC table. An ATM port reset was required to recover from the problem. This problem has been corrected. 8. IBM 8271 switch with ATM UFC experiencing up-link receive failures, requiring a reset of the ATM UFC has been corrected. Release 1.10.0 1. A problem where the ATM UFC used the wrong virtual circuit connection in the case of a call collision has been corrected. It is recommended to upgrade ALL ATM UFCs in your network to avoid interoperability problems with previous releases. In the case of a call collision, the call placed by the ATM LAN Emulation Client with the lower ATM address is to be used. In previous releases, each octet of the called ATM address was compared with the corresponding octet of the calling ATM address until a pair of octets was found that were not equal. If either of the octets of this pair contained a '1' in the most significant bit, the wrong switched virtual circuit would be used in the case of a call collision. The effects of this problem were observable when attempting to call an ATM LAN Emulation Client that did NOT contain this defect. 2. A problem where end-station to end-station connectivity across the ATM network was lost has been corrected. If a data direct virtual circuit connection was taken down at a time when a duplicate data direct virtual circuit connection existed, the ATM UFC did not update the necessary hardware filter tables to maintain end-station to end- station connectivity. 3. Users having intermittent connectivity problems through the ATM UFC has been corrected: + Under heavy traffic, the ATM UFC may not learn a burst of more than 200 addresses. + End-station to end-station connectivity across the ATM Network is lost. 4. The switch resetting the ATM UFC due to "Echo Response" time-out has been resolved, specifically: + Heavy traffic through the ATM UFC. 5. The time the ATM UFC takes to rejoin the ATM Emulated LAN has been shortened. For environments that include MSS redundancy, the switching time from primary MSS to backup MSS and vice-versa is improved. 6. User having to reset the switch multiple times to get the ATM UFC registered has been corrected. 7. The ATM UFC incorrectly responded to all LE_ARP REQUESTS for MAC address 00:00:00:00:00:00 has been fixed. Known Problems / Anomalies / Design Points 1. IMPORTANT NOTICE: RULES for upgrading ATM UFC boot(strap) code. Please read ALL four rules. 1. Token-Ring switch users REQUIRE ATM UFC boot(strap) code Release 1.01.0 or later for proper operation of the ATM UFC. 2. For Ethernet Switch users, ATM UFC boot(strap) code Release 1.01.0 or later is recommended. 3. ATM UFC boot(strap) code Releases 1.13.0 through 1.14.1 are defective. These releases should not be installed. If a defective release of boot(strap) code has been installed, upgrading to a later release is recommended. 4. ATM UFC load (Boot) time is four times faster using boot(strap) Release 1.12.3, 1.14.2 (or later) than earlier releases. Upgrading boot(strap) code to take advantage of this performance improvement is optional. To determine the ATM UFC boot (strap) version installed in your ATM UFC(s), follow the following steps: 1. From the switch log-on screen, enter the password "diag" (no "") followed by the user-defined password. For example, if the user-defined password is "hello", then enter "diaghello". If there is no user-defined password then enter "diag". 2. Select the AFC Debug Console option on this menu. Then enter the ATM UFC port number when prompted. 3. Hit ENTER one or more times just to make sure you have connected to the ATM UFC debug console. 4. Enter the command VPD (case sensitive). This will display version information for both the operational (MAIN) image and the boot(strap) (BOOT) image. 5. Consult the RULES above to determine if your boot(strap) code should be replaced. If you plan to replace the boot(strap) code see the section titled Loading the ATM UFC boot(strap) Image for an explanation of the ATM UFC boot code download procedure. If you do not plan to replace the boot(strap) code then enter the command exit (case sensitive) or ctrl-b to leave the AFC Debug Console. 2. DO NOT PLUG OR UNPLUG THE ATM UFC WHILE THE 8270, 8271, OR 8272 IS POWERED ON. Inserting or removing the UFC with the LAN Switch powered on could result in permanent damage to the UFC. 3. The LAN segment number must be assigned, using the Source-Route Configuration Panel, when the ATM UFC is used in a Token-Ring source-routed network. The above action prevents IBM 8270/8272 LAN Switch learning the LAN segment number from explorer traffic on the network. The ATM LEC resets when the LAN segment number is learned from explorer traffic. The ATM LEC reset will disrupt any existing traffic. For information on how to assign the LAN segment number, see the IBM 8270/8272 LAN Switch Planning and Installation Guide. 4. MAXIMUM VCCs -Table 1-1 on page 1-4 of the ATM 155-Mbps Multimode Fiber UFC - Planning and Installation Guide indicates that the ATM 155 UFC can support 3072 VCCs distributed over all active LAN Emulation Clients This release of the ATM 155 UFC will support only 1000 data direct VCCs. The 1000 data direct VCCs are shared by the maximum 8 active LAN Emulation Clients. 5. MAXIMUM LE_ARP TABLE SIZE - The LE_ARP table size is limited to 3400 entries for this release of the ATM 155 UFC software. The 3400 entries are shared by all active LAN Emulation Clients. In the case of overflow, the ATM UFC will remove one of the last 340 entries to make room for the new one. 6. The two LED patterns shown in the ATM 155-Mbps Multimode Fiber UFC - Planning and Installation Guide, Chapter 6, Table 6-2, page 6-4, first row, show normal operational status. Users experiencing network problems when either of these patterns is present should consult the Alternate Trouble Indicators listed in the fourth column of the table. 7. If user experiences connection delays, it is recommended that the Maximum Unknown Frame Count (C10) parameter be set to 10. 8. We now recommend that the Maximum unknown frame time (C11) and the Expected LE_ARP Response Time (C20) be the default value. 9. Data Direct VCC Keep Alive Timeout. This configurable parameter replaces the "Data Direct VCC after BUS failure" parameter found in early releases of the 827x ATM UFC Feature. The data direct VCC keep alive timeout allows a user to configure how long the 827x ATM Feature will maintain its data direct VCCs to other LAN Emulation Clients, after it has detected unavailability of the LES/BUS. If a data direct connection existed prior to a disruption, and the ATM address of the station was learned prior to the LES/BUS connection disruption, then traffic to and from the station continues to flow during the temporary disruption of the LES/BUS connection. The ATM Forum specifies that data direct VCCs should be taken down immediately upon detection of LES/BUS unavailability. Enter 0 seconds for 100% ATM Forum Compliant operation. If your network contains an alternate path to any of the destinations that are reachable through the ATM network, (for example, an Ethernet, Token-Ring, or alternate ATM path), you must set the data direct keep alive timeout small enough to avoid loops in your network. (You must also enable the 802.1D spanning tree protocol to avoid loops in your network). The data direct keep alive timeout plus the time that it takes the LEC to discover the absence of the LES/BUS must be smaller than the 802.1D spanning tree parameters Max Age plus Forward Delay for your network. Data Direct Keep Alive Timeout plus LES/BUS Failure Detection Time (4 seconds maximum) must be set less than or equal to 802.1D Max Age plus 802.1D Forward Delay. Spanning tree loops can be created if the above recommendation is not followed. The following diagram shows a network that has two paths between the ATM network and the token ring network. The 'backup' path is blocked by the 802.1D spanning tree protocol. ---------------------------------------------------------------------- ..................... . . . ATM ELAN . ..................... | | | XXX - port blocked by spanning tree | | ----------- ----------- | 827x - A | | 827x - B | ----------- ----------- | | ;...........; . token-ring . . - or - . . ethernet . ............. ---------------------------------------------------------------------- Assume that the ATM port of the 827x-B is blocked by the 802.1D spanning tree. It will remain in blocked state as long as BPDUs are received on that port. If the LES/BUS fails and no BPDUs are received for the MAX AGE time, the port will transition to the LISTENING state followed by the LEARNING state and then the FORWARDING state. The port will stay in LISTENING state for one forward delay time and in LEARNING state for one forwarding delay time. So, if the port fails to receive BPDUs for MAX AGE plus two times the FORWARD DELAY time, it will transition to the FORWARDING state. If the LES/BUS outage is short enough so that the Data Direct VCC Keep Alive Timeout timer is still running, the ATM UFC will not signal a LINK DOWN state to the spanning tree code. When the LES/BUS VCCs are reestablished, the ports are re-attached to the ELAN as if there was no interruption. If the Data Direct VCC Keep Alive Timeout is set too long, both ports could be reattached to the ELAN in FORWARDING state causing a spanning tree loop. Frames can endlessly circulate in a loop causing extreme network congestion. Recommended settings for 802.1D spanning tree and Data Direct VCC Keep Alive Timeout Parameter, Case 1, Case 2 802.1D Max Age, 20 sec., 6 sec. 802.1D Forward Delay, 15 sec., 4 sec. Data Direct VCC Keep Alive Timeout, 31 sec., 6 sec. The ATM UFC detects LES/BUS failures in a maximum of 4 seconds. A LES/BUS failure is detected if any of the control or multicast VCCs are released or if there were no packets received on any of the control or multicast VCCs for a period of 4 seconds. If the network is idle, 4 seconds of inactivity is normal. The ATM UFC will send an LE_ARP request for the all Fs mac address every second that the network is idle to distinguish between an idle network and a LES/BUS failure. ----------------------------------------------------- Configuration screen showing the Data Direct VCC Keep Alive Timeout parameter ----------------------------------------------------- Advanced Configuration of a LEC - LAN Emulation Enhancements Slot 1 LEC Index 101 Port is UP Current Default LAN Emulation Enhancements Value Value Data Direct VCC Keep Alive Timeout 6 sec 34 sec Save and Cancel and Return Return Restore Defaults Save changes made to this panel and return to the previous panel Use cursor keys to choose item. Press to confirm choice. Press to return to Main Menu. ----------------------------------------------------- 8260/8265 Specific Information 1. For installations of the 8272 LAN Switch Modules FC 5208 and FC 5308, the recommended software level for the 8260 ATM Control Point and Switch Module (CPSW) is v.3.1.8 or higher. 2. For installations of the 8272 LAN Switch Modules FC 5208 and FC 5308, the recommended software level for the 8265 ATM Control Point and Switch Module (CPSW) is v.3.3.2 or higher. 3. 8272 LAN Switch Module derives its power and cooling from the 8260/8265 Hub. 4. To install a Universal Feature Card (UFC) AFTER the LAN Switch Module has already been installed in an 8260 Hub, remove the Switch Module from the Hub in order to power OFF the module prior to installing the UFC. Then, beginning with step 2, follow the instructions contained in the Planning and Installation Guide, shipped with the specific UFC, in the section "Installing a Universal Feature Card." 5. In configurations where FC 5208 or FC 6208 is inserted in positions 16 and 17 of an 8260 or where FC 5308 or FC 6308 is inserted in positions 15, 16 and 17 of an 8260, potential mechanical interference can occur when certain Universal Feature Cards (UFCs) are inserted in position 17. It is best to avoid position 17 when installing the 8272 LAN Switch Modules. If this can not be avoided, the UFC can be inserted with care. Files on the Diskettes and Software Download Procedures * IBM 827X ATM UFC Microcode and SNMP MIB Diskette - Release 1.15.5 File Name, Contents Notes ATM_1155.UFC : ATM UFC main image and boot(strap) code (1) RFC1695.MIB : ATM MIB (2) RFC1695.DEF : ATM MIB Compiler Object Definition (2) LECMIB.MIB : LAN Emulation Client MIB (2) LECMIB.DEF : LEC MIB Compiler Object Definition (2) README.ATM : 8270/8271/8272 ATM UFC Release Notes, Version (2) 1.15.5, plain text READ_ATM.HTM : 8270/8271/8272 ATM UFC Release Notes, Version (2) 1.15.5, html format NOTES 1. This is the software module to be installed on the ATM UFC. 2. These are network management files that should be given to your network administrator. Loading the Latest ATM UFC Main Image To load the latest ATM UFC software using TFTP, the following procedure is recommended: 1. Select Download from the main menu. 2. From the Download menu, select TFTP to be used for the download. 3. Set the Download Image to UFC Image. 4. Set the Download Filename to ATM_1155.UFC 5. Select Execute Network Download. 6. You must reset the port to activate the new ATM UFC image. Loading the ATM UFC boot(strap) Image WARNING: WARNING: THIS PROCEDURE MUST BE FOLLOWED EXACTLY TO AVOID RENDERING THE ATM UFC PERMANENTLY INOPERABLE, REQUIRING A NEW ATM UFC. READ AND UNDERSTAND THESE INSTRUCTIONS BEFORE ATTEMPTING TO DOWNLOAD THE ATM UFC BOOT(STRAP) CODE. IF YOU HAVE ANY QUESTIONS, OR PREFER TO BE GUIDED THROUGH THE ATM UFC BOOT(STRAP) UPDATE PROCEDURE, CALL IBM SUPPORT. To minimize the risk of failing to recover from an incomplete ATM UFC boot download, the following additional items are recommended: 1. Use the 827X LAN Switch console to access the download menus (instead of Telnet). 2. Choose a time to upgrade the boot code when ATM UFC traffic is least heavy, or move the file server containing the ATM UFC image to a LAN port on the switch you are modifying (instead of on the ATM port). 3. A failed download can take up to 1 minute to timeout. Please be patient for it to terminate so that built-in recovery code has a chance to execute. 4. Retry failed boot download as soon as possible and before the 827X or the ATM UFC port is reset. Follow the steps below to update the ATM UFC boot(strap) code. Notice that these steps require that you download the new ATM UFC image as you normally do, reset the adapter, and follow special, additional steps to load new boot(strap) code to the ATM UFC. BOTH DOWNLOADS ARE REQUIRED TO ENSURE SAFE RECOVERY IN THE EVENT OF AN UNSUCCESSFUL DOWNLOAD. IF YOU HAVE ATM UFC OPERATIONAL (MAIN) CODE AT VERSION 1.15.0 OR LATER, THEN YOU CAN SAFELY SKIP TO STEP 2. * [STEP 1] To prepare your system for safe ATM UFC boot(strap) download: a. Download the new ATM UFC main image (ATM_1155.UFC) to the ATM UFC. (see the section above titled Loading the Latest ATM UFC Main Image) b. Reset the ATM UFC port (or optionally, reset the entire switch) so that the new image is operational. This includes the support for safer boot(strap) download. * [STEP 2] To download the new ATM UFC boot(strap) from the ATM_1155.UFC image file: a. From the switch log-on screen, enter the password "diag" (no "") followed by the user-defined password For example, if the user-defined password is "hello", then enter "diaghello". If there is no user-defined password then enter "diag". b. Select the AFC Debug Console option on this menu. Then enter the ATM UFC port number when prompted. c. Hit ENTER one or more times just to make sure you have connected to the ATM UFC debug console. d. Enter the command "F2" (case sensitive, and no ""). This "enables" the boot(strap) code on the ATM UFC to be erased and reloaded with the next download to the adapter. You should see a message printed that confirms your request. If you do not see a message, try to enter the command again. Do not reset the switch or the ATM UFC before starting the download (see below). If you do, you will need to re-issue the "F2" command, as it is not saved following an ATM UFC reset. e. Enter the command VPD and RECORD the serial number and burned-in MAC address for future reference. f. Enter the command exit (case sensitive) or ctrl-B, and ctrl-N, to return to the switch console. If you are in TELNET, ctrl-B will take you out of TELNET, that is okay. TELNET back to the switch to return to the log-on screen. g. Download the ATM UFC code to the ATM UFC. WARNING: YOU CAN ONLY SELECT TFTP DOWNLOAD. A SERIAL PORT DOWNLOAD OF THE ATM UFC WILL RESTART THE ATM UFC, WHICH BY DEFAULT, RE-APPLIES WRITE PROTECTION TO THE BOOT CODE IN THE ATM UFC. Failure to complete the download of boot(strap) code IS FATAL to the adapter if you reset it before successfully completing the download. * [STEP 3] To verify that the download of boot(strap) code to the ATM UFC was successful: a. From the switch logon screen, enter the password "diag" (no "") followed by the user-defined password. For example, if the user-defined password is "hello", then enter "diaghello". If the user has not defined a password just enter "diag". b. Select the AFC Debug Console option on this menu. Then enter the ATM UFC port number when prompted. c. Hit ENTER one or more times just to make sure you have connected to the ATM UFC debug console. d. Enter the command VPD (again, case sensitive). This will display version information for both the operational (MAIN) image and the boot(strap) (BOOT) image. The BOOT image should be updated to the same version as the UFC download file (i.e. ATM_1155.UFC is version 1.15.5). Note the main image will not be updated to the same version until the ATM UFC is reset. If the boot image is not updated or is incorrect, DO NOT RESET THE UFC or SWITCH. DO NOT ATTEMPT A SERIAL DOWNLOAD to the ATM UFC. You can go back to step 2 and attempt to download the boot(strap) code again (TFTP only). If the version information for the BOOT image has not changed, it is likely that you did not enter the "F2" command in [STEP 2], or that you performed a SERIAL download instead of a TFTP download in [STEP 2]. If you are still unable to upgrade the ATM UFC Boot code, contact IBM Support before resetting the adapter or switch. back to top of document END OF RELEASE NOTES